Memory system quality threshold intersection analysis and configuration

ABSTRACT

A memory quality engine can improve the operation of a memory system by setting more effective operating parameters, disabling or removing memory devices unable to meet performance requirements, and providing evaluations between memory populations. These improvements can be accomplished by converting quality measurements of a memory population into CDF-based data, formulating comparisons of the CDF-based data to metrics for quality analysis, and applying the quality analysis. In some implementations, the metrics for quality analysis can use one or more thresholds, such as a system trigger threshold or an uncorrectable error correction condition threshold, which are set based on the error correction capabilities of a memory system. Formulating the comparison to these metrics can include determining an intersection between the CDF-based data and one of the thresholds.

CROSS-REFERENCE TO RELATED APPLICATIONS

The applications titled “Memory System Quality Margin Analysis and Configuration” with Ser. No. 15/981,835 and titled “Memory System Quality Integral Analysis and Configuration” with Ser. No. 15/981,829, both filed herewith, are each herein incorporated by reference in their entirety.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to improving memory system functionality through advances in memory component threshold intersection analysis and resulting configurations of the memory system.

BACKGROUND

A memory system can be a storage system, such as a solid-state drive (SSD), and can include one or more memory components that store data. For example, a memory system can include memory devices such as non-volatile memory devices, volatile memory devices, or a combination of both. In general, a host system can utilize a memory system to store data at the memory devices of the memory system and to retrieve data stored at the memory system.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure. The drawings, however, should not be taken to limit the disclosure to the specific embodiments, but are for explanation and understanding only.

FIG. 1 illustrates an example computing environment in accordance with some implementations of the present disclosure.

FIG. 2 is a conceptual diagram of an example of acting on memory quality data to improve memory performance.

FIG. 3 is a block diagram of components which, in some implementations, can be used in a system employing the disclosed technology.

FIG. 4 is a flow diagram of a process used in some implementations for applying a quality analysis to CDF-based data, to improve memory systems.

FIG. 5 is a flow diagram of a process used in some implementations for formulating an intersection comparison between CDF-based data and metrics.

FIG. 6 is a conceptual diagram of an example graph of quality measurements, expressed as a codeword/bit error count histogram.

FIG. 7 is a conceptual diagram of an example of CDF-based data generated from the quality measurements of FIG. 6.

FIG. 8 is a conceptual diagram of example analysis results for the CDF-based data of FIG. 7.

FIG. 9 is a conceptual diagram of example of CDF-based data indicating a memory population as an extrinsic outlier.

FIG. 10 is a block diagram of an example computer system in which embodiments of the present disclosure can operate.

The techniques introduced here may be better understood by referring to the following Detailed Description in conjunction with the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements.

DETAILED DESCRIPTION

Existing memory analysis systems fail to provide metrics useful to adequately optimize memory systems performance, diagnose memory system quality or remaining life and do not effectively provide results in a manner that facilitates analytical connections between data sets.

Aspects of the present disclosure a memory quality engine that address the above and other deficiencies by implementing analyses of quality measurements in terms of cumulative distribution function (CDF) based data. The memory quality engine can perform analysis on memory units at different granularities, where a quality measurement corresponds to each unit of memory under analysis of the granularity size. For example, the granularity of the analysis can be one of: a block level, page level, codeword level, region level, whole device level, or a level corresponding to multiple devices within a memory system, etc. The memory under analysis for which quality measurements are taken is referred to herein as the “memory population.” For example, a memory population can be any memory system such as a subset of the memory within a single memory device, all the memory of a memory device, or memory from multiple memory devices. A memory system can be a storage system, such as a solid-state drive (SSD). In some embodiments, a memory system is a hybrid memory/storage system. In various implementations, memory devices can include non-volatile memory devices, such as, for example, negative-and (NAND).

In some implementations, the memory quality engine can obtain the quality measurements in terms of frequency of memory units for given error counts. In some implementations, the quality measurements can be histograms of this data, where the independent variable is a number of errors or other quality measure and the dependent variable is the number of memory units that have that number of errors. The memory quality engine can convert the quality measurements into CDF-based data, e.g. as one minus the CDF of the histogram quality measure, on a logarithmic scale. While the embodiments described herein are described in terms of quality analysis for memory populations, analysis and improvement can also be performed for other technologies for which quality data measures can be obtained.

Once the memory quality engine has CDF-based data, it can perform a quality analysis by formulating comparisons of the CDF-based data to metrics. In some implementations, the metrics for quality analysis can use one or more thresholds, such as a system trigger threshold or an uncorrectable error correction condition (UECC) threshold, which are set based on the error correction capabilities of a memory system. Formulating the comparison to these metrics can include determining an intersection between the CDF-based data and one of the thresholds. An intersection with the system trigger threshold is referred to as a “trigger rate,” and intersection with the UECC threshold is referred to as a “UECC rate.” These intersections can be a measure of the health of the memory population. More specifically, where a threshold indicates performance level (e.g. a maximum count of errors), the intersection of the CDF-based data with the threshold can show how many memory units in the memory population are expected to be below the performance level. In some implementations, the CDF-based data may not actually intersect with a given threshold because the memory population was too small to have a memory unit with the specified number of errors. However, the CDF-based data can be fitted to a function (such as a liner function) and the intersection of the function with the threshold can be used as the health measure instead of an actual intersection.

Using results of the quality analysis, the memory quality engine can make improvements to a memory system that includes the memory population. In some implementations, the improvements can include comparing the quality analysis results to a threshold to classify the memory population as being acceptable or being unacceptable. Where the memory population is unacceptable, it can be added to a data structure identifying questionable memory, it can be disabled, or it can be flagged for removal from the memory system. In some implementations, multiple thresholds can be used to classify the memory population into one of multiple corresponding categories, which can have associated actions. For example, a set of categories can be: high performing drive—available for critical use; acceptable drive—available for standard use; low performing drive—available for low-priority use, schedule further quality checks; or drive failure—schedule data transfer and deactivation.

Application of the methods and systems described herein provides a number of technical improvements, e.g. for memory devices, processing units, or other devices for which quality measurements can be taken. A memory drive, for example, can be configured to operate faster than would otherwise be possible by virtue of having a measure of how close the drive is to a failure condition. More specifically, an effective analysis of quality measurements can include determining a safety margin that a particular drive has before reaching a failure condition and, where that safety margin is sufficiently large, adjusting operating parameters of the drive to increase drive performance (e.g., speed, latency, energy efficiency, etc.). This performance increase can then be achieved without undue concern for the drive passing into a failure condition. A similar procedure could be performed on technologies besides memory, such as to accelerate a CPU, adjust power consumption levels (e.g. using voltage levels and fan speeds), etc.

As another example, a memory system can be made more reliable through meaningful determinations of the health of a memory population, at various granularities. In some implementations, population health measures can be used to identify and disable drives with insufficient health. More specifically, a health measure for a memory population, such as a trigger rate or UECC rate, can be compared to a corresponding health threshold. Where the health measure is below the threshold, the memory population can be disabled or removed from a memory system. In some implementations, health measures can be used to classify or sort a set of memory populations. For example, an intersection point health measure for each of a set of memory populations can be used to match memory populations with storage functions, based on how critical the storage functions are. More healthy memory populations can be assigned more critical storage functions, while less healthy populations can still be used for less critical storage functions.

As yet another example of technical improvements offered by this technology, particular memory populations can be identified as defective, e.g. for removal or replacement. This can be accomplished by identifying an “extrinsic tail” for a memory population. An extrinsic tail can be identified using a projection of CDF-based data. As used herein a “projection” can be determined in various ways. In some implementations, the projection of the CDF-based data can be a best fit of the CDF-based data to a linear function. In some implementations, other modeling techniques can be used to determine the projection, such as using a function of a different degree, using the average of CDF-based data from other memory populations, or applying a machine learning algorithm to the CDF-based data or data of other memory populations to predict next data points from previous data points of the CDF-based data. In some implementations, the projection can be based on a portion of the CDF-based data. An extrinsic tail can be identified by comparing the projection to the actual CDF-based data and determining if a variance at higher error rate values deviates from the projection beyond a specified degree. Identifying an extrinsic tail can indicate the corresponding memory population is in some way defective, allowing corrective action to be taken. A pattern of defective devices can also be analyzed, e.g. to determine that particular parts, drive manufactures, etc. are more likely to produce defective memory populations.

This technology also provides new abilities to make analytical connections between data sets. For any given quality metric, the CDF-based data can be reliably compared across device types, device sources, operational parameters, etc. This allows for the dependent variables to be external factors. For example, two memory devices can have different components, sizes, manufactures, construction processes, etc. Comparisons of their CDF-based analytics can show how these external factors affect device performance.

Several implementations are discussed below in more detail in reference to the figures. FIG. 1 illustrates an example computing environment 100 in accordance with some implementations of the present disclosure. The computing environment 100 can comprise hardware components that provide memory analysis and configuration. Computing environment 100 can include one or more input devices 120 that provide input to the CPU(s) (processor) 110, notifying it of actions. The actions can be mediated by a hardware controller that interprets the signals received from the input device and communicates the information to the CPU 110 using a communication protocol. Input devices 120 can include, for example, a mouse, a keyboard, a touchscreen, an infrared sensor, a touchpad, a wearable input device, a camera- or image-based input device, a microphone, or other user input devices.

CPU 110 can be a single processing unit or multiple processing units in a device or distributed across multiple devices. CPU 110 can be coupled to other hardware devices, for example, with the use of a bus, such as a PCI bus or SCSI bus. The CPU 110 can communicate with a hardware controller for devices, such as for a display 130. Display 130 can be used to display text and graphics. In some implementations, display 130 provides graphical and textual visual feedback to a user. In some implementations, display 130 includes the input device as part of the display, such as when the input device is a touchscreen or is equipped with an eye direction monitoring system. In some implementations, the display is separate from the input device. Examples of display devices are: an LCD display screen, an LED display screen, a projected, holographic, or augmented reality display (such as a heads-up display device or a head-mounted device), and so on. Other I/O devices 140 can also be coupled to the processor, such as a network card, video card, audio card, USB, firewire or other external device, camera, printer, speakers, CD-ROM drive, DVD drive, disk drive, or Blu-Ray device.

In some implementations, the computing environment 100 also includes a communication device capable of communicating wirelessly or wire-based with a network node. The communication device can communicate with another device or a server through a network using, for example, TCP/IP protocols. Computing environment 100 can utilize the communication device to distribute operations across multiple network devices.

The CPU 110 can have access to a memory 150 in a device or distributed across multiple devices. A memory includes one or more of various hardware devices for volatile or non-volatile storage, and can include both read-only and writable memory. For example, a memory can comprise random access memory (RAM), various caches, CPU registers, read-only memory (ROM), and writable non-volatile memory, such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, device buffers, and so forth. A memory is not a propagating signal divorced from underlying hardware; a memory is thus non-transitory. Memory 150 can include program memory 160 that stores programs and software, such as an operating system 162, memory quality engine 164, and other application programs 166. Memory 150 can also include data memory 170 that can include quality measurements (e.g. histograms of quality data), CDF-based data obtained from quality measurements, memory usability thresholds, comparison metrics, action triggers, configuration data, settings, options or preferences, etc., which can be provided to the program memory 160 or any element of the computing environment 100.

Some implementations can be operational with numerous other computing system environments or configurations. Examples of computing systems, environments, and/or configurations that may be suitable for use with the technology include, but are not limited to, personal computers, server computers, handheld or laptop devices, cellular telephones, tablet devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, or the like.

FIG. 2 is a conceptual diagram of an example 200 of acting on memory quality data to improve memory performance. Example 200 includes computing device 205, examples of which can include computing environment 100. Computing device 205 can operate in a networked environment using logical connections through network 230 to one or more sources of quality measurements, such as server systems 220.

Server systems 220 can comprise computing systems, such as computing environment 100. Though each version of device 100 is displayed logically as a computing system, these devices can each be a distributed computing environment encompassing multiple computing devices located at the same or at geographically disparate physical locations. Computing device 205 and server systems 220 can each act as a server or client to other server/client devices. Server systems 220A-C can each connect to storage devices 225A-C. In example 200, storage devices 225A-C make us the memory population under analysis. Though storage devices 225 are displayed logically as single units, storage devices 225 can each be a distributed computing environment encompassing multiple computing devices, can be located within their corresponding server, or can be located at the same or at geographically disparate physical locations.

Network 230 can be a local area network (LAN) or a wide area network (WAN), but can also be other wired or wireless networks. Network 230 may be the Internet or some other public or private network. Computing device 205 and server systems 220 can be connected to network 230 through network interfaces, such as by wired or wireless communication. While the network connections are shown as separate connections, these connections can be any kind of local, wide area, wired, or wireless network, including network 230 or a separate public or private network.

In operation, example 200 begins with steps 252A-C, where server systems 220 obtain quality measures for their corresponding storage devices 225A-C. In example 200, these quality measures are histograms 207A-C, which are the counts of bit errors per codeword in the storage devices 225. Through steps 254A-C and 256, these quality measures 207 are provided to computing device 205. An example of the histogram data 207A is provided in FIG. 6.

At step 258, computing device 205 converts the histograms 207 into CDF-based data 260 (1-CDF). Individual histograms 207 are averaged to obtain an overall histogram for conversion to CDF-based data 210. An example of the histogram data 210 is provided in FIG. 7. At step 260, computing system 205 formulates comparisons of the CDF-based data to metrics for quality analysis. This analysis can include determining an intersection between the CDF-based data and one or more thresholds (e.g. a system trigger threshold or a UECC threshold). In some implementations, this analysis can include determining an intersection between the one or more thresholds and a projection of the CDF-based data. Additional details regarding the quality analysis are provided in relation to FIGS. 4 and 5.

Based on the quality analysis results, computing device 205 can determine actions to take with regard to storage devices 225. In this example, the analysis results 215 indicate that the memory population is only moderately healthy, and thus should only be tasked with non-critical storage operations. At steps 262, 264A-C, and 266A-C, computing device 205 can communicate this determined action to storage devices 225A-C, causing them to be adjusted accordingly. Here, because results 215 indicate a health level of the memory population including storage devices 225 as being below a health threshold, adjustment at 266A includes setting storage devices 225A to be unavailable for critical storage functions.

FIG. 3 is a block diagram of components 300 which, in some implementations, can be used in a system employing the disclosed technology. The components 300 include hardware 302, general software 320, and specialized components 340. As discussed above, a system implementing the disclosed technology can use various hardware including processing units 304 (e.g. CPUs, GPUs, APUs, etc.), working memory 306, storage memory 308 (local storage or as an interface to remote storage), and input and output devices 310. In various implementations, storage memory 308 can be one or more of: local devices, interfaces to remote storage devices, or combinations thereof. For example, storage memory 308 can be a set of one or more hard drives (e.g. a redundant array of independent disks (RAID)) accessible through a system bus or can be a cloud storage provider or other network storage accessible via one or more communications networks (e.g. a network accessible storage (NAS) device). Components 300 can be implemented in a client computing device such as client computing devices 205 or on a server computing device, such as server computing device 220.

General software 320 can include various applications including an operating system 322, local programs 324, and a basic input output system (BIOS) 326. Specialized components 340 can be subcomponents of a general software application 320, such as local programs 324. Specialized components 340 can include CDF converter 344, intercept analysis engine 346, analysis application engine 350, and components which can be used for providing user interfaces, transferring data, and controlling the specialized components, such as interface 342. In some implementations, components 300 can be in a computing system that is distributed across multiple computing devices or can be an interface to a server-based application executing one or more of specialized components 340.

CDF converter 344 can receive a set of quality measurements, e.g. via interface 342, and convert the quality measurements to CDF-based data. In some implementations, the quality measures can be a histogram specifying quality measures in relation to a memory population, e.g. bit errors per memory unit, read, write, or erase times, etc. In various implementations, the quality measures can be measures of other metrics such as an “x-cuttoff” or can iterate on results of a quality analysis. As an example of a x-cuttoff implementation, each histogram in a set of quality measures can have a highest value on the x-axis. Where the x-axis measures bits in error, for example, this can be the highest measured number of bits in error, referred to as the “x-cuttoff.” In FIG. 6, for example, the highest bit in error count, and thus the x-cuttoff, is at 31 bits in error. Another histogram can be created using ranges of x-cuttoffs as the histogram buckets and the count of histograms with an x-cuttoff in that range as the count for that bucket.

As discussed below, quality analysis results can include values such as margins from a threshold, intersections with a threshold, areas under a CDF-based data curve, ratios of such areas as compared to the area of a rectangle containing the CDF-based data curve, and identifications of extrinsic tails. Any of these values taken for multiple different memory populations can be measured in terms of a histogram and used by the process described herein in a second level quality analysis among memory populations.

CDF-based data is data that incorporates the CDF function of a set of data, where the CDF is the function whose value is the probability that a corresponding continuous random variable has a value less than or equal to a given value. For example, in terms of error measures of codewords in memory, the CDF-based data can specify, for a given amount of errors, the frequency of codewords that are expected have no more than that amount of errors. In some implementations, the CDF-based data can be 1-CDF, where the CDF is taken relative to the received histogram of quality measures.

Intercept analysis engine 346 can receive a threshold through interface 342 and can determine an intercept between the threshold and CDF-based data from CDF converter 344. In some implementations, instead of finding the interception between the threshold and CDF-based data, intercept analysis engine 346 can first determine a projection of the CDF-based data, e.g. by fitting the CDF-based data to a function. Intercept analysis engine 346 can then determine an intercept between the threshold and the projection of the CDF-based data. This intercept can be a health measure of the memory population.

Analysis application engine 350 can determine whether an action has been mapped to the results of the analysis, and if so, cause the action to be taken. Examples of actions that can be mapped to various analysis results include: modifying operating parameters of a memory population to increase speed or reliability, specifying types of storage operations that a memory population is allowed to perform, or disabling or removing a memory population from a memory system. For example, depending on the intercept value computed by intercept analysis engine 346, analysis application engine 350 can make a corresponding adjustment to an operating parameter of the memory population. As a more specific example, a clock used for operations on the memory population can be decreased based on a normalization of the intercept value. As another example, if the intercept value is above a threshold amount, the memory population can be marked for use on critical storage tasks.

Those skilled in the art will appreciate that the components illustrated in FIGS. 1-3 described above, and in each of the flow diagrams discussed below, may be altered in a variety of ways. For example, the order of the logic may be rearranged, substeps may be performed in parallel, illustrated logic may be omitted, other logic may be included, etc. In some implementations, one or more of the components described above can execute one or more of the processes described below.

FIG. 4 is a flow diagram of a process 400 used in some implementations for applying a quality analysis to CDF-based data, to improve memory systems. The method 400 can be performed by processing logic that can include hardware (e.g., processing device, circuitry, dedicated logic, programmable logic, microcode, hardware of a device, integrated circuit, etc.), software (e.g., instructions run or executed on a processing device), or a combination thereof. In some embodiments, the method 400 is performed by the memory quality engine 164 of FIG. 1. Although shown in a particular sequence or order, unless otherwise specified, the order of the processes can be modified. Thus, the illustrated implementations should be understood only as examples, and the illustrated processes can be performed in a different order, and some processes can be performed in parallel. Additionally, one or more processes can be omitted in various embodiments. Thus, not all processes are required in every implementation. Other process flows are possible. At block 404, process 400 can obtain quality measurements for a memory population under examination. In some implementations, process 400 can obtain the quality measurements in terms of frequency of memory units for a given error count. For example, the memory unit can be logical structures of the memory population, a portion of memory hardware, or multiple memory devices. More specific examples of memory units include blocks, pages, lines, codewords, regions, sectors, die, cells, drives, server racks, clusters, etc. The quality measures can be of various types such as bit error counts, faults, read operation execution times, write operation execution times, erase operation execution times, etc. In some implementations, the quality measures can be in the form of histogram data. The histogram can represent the count, for a given amount of errors, of the memory units that had that amount of errors. In some implementations, the quality measures can be quality measures for multiple items under analysis. For example, each drive in a memory population can provide a separate set of quality measures. As discussed above, while the figures are discussed in terms of quality measures for memory populations, the systems and methods described herein can also apply to other technologies. For example, the quality measures can be in relation to CPUs, networks, displays, power units, etc. In some implementations, the quality measures can be for non-computing measures such as engine performance, delivery times, material durability, etc. An example graph illustrating sample quality measures is provided in relation to FIG. 6.

At block 406, process 400 can convert the obtained quality measurements into CDF-based data. In some implementations, the CDF-based data is the CDF of the received quality measures. In some implementations, process 400 can generate the CDF-based data by taking the CDF of the received quality measures, then using 1-CDF as the CDF-based data. In cases where the received quality measures are multiple sets for various memory units, process 400 can either first average the histograms before generating the CDF-based data or process 400 can create CDF-based data for each set, and combine (e.g. sum) the results. In some implementations, the CDF-based data can be on a logarithmic scale. An example graph illustrating sample CDF-based data is provided in relation to FIG. 7.

At block 408, process 400 can formulate a comparison of the CDF-based data to metrics for a quality analysis of the memory population. Formulating this comparison can include determining where the CDF-based data, or where a projection of the CDF-based data, intersects with a threshold condition. Such an intersection can indicate an expected rate that memory units in the memory population are expected to have at least a quality condition set by the threshold. For example, where the threshold condition is bit error count and the CDF-based data indicates frequency of codewords given a maximum bit error count, the intersection of the threshold condition with the CDF-based data can show an expected rate within the memory population that memory units are expected to have at least the failure bit error count. Additional details regarding formulation the comparison to CDF-based data are provided below in relation to FIG. 5. An example graph illustrating results of block 408 are provided in relation to FIG. 8.

At block 410, process 400 can apply results of a quality analysis to make improvements in a memory system by causing actions in relation to the memory population. In various implementations, whether or what action to cause can be determined: by determining a comparison metric for the memory population by applying one or more thresholds to the results of the quality analysis, by categorizing the memory population based on the results of the quality analysis, or by comparing portions of the quality analysis to expected or projected results. More specifically, in some implementations, a comparison metric can use a pass/fail threshold established for analyzing a memory population which can be compared to analysis results (e.g. a margin or health value). In some implementations, the comparison metric can map scores from the quality analysis into categories. For example, the possible health scores can be divided into three ranges, amounting to “good,” “acceptable” and “bad” classifications. The delimiting values for these ranges can be set based on a historical analysis of memory populations with various health scores, and how efficiently or reliably devices with various scores performed memory operations.

In some implementations, the comparison metrics can compare the quality analysis results from multiple executions of process 400 to categorize differences between memory populations. For example, the analysis results from a memory population that originated from a first factory can be compared to results from a memory population that originated from a second factory, where the difference can be used to score the factory. As another example, because the analysis results can be compared across device types, a memory population that is made up of a first type of memory devices can be compared to results from a memory population that is made up of a different type of memory devices.

In some implementations, the comparison metrics can use the analysis results as input to a function configured to determine an adjustment amount for a memory system. For example, an intersection analysis result can be used as a parameter to a function that specifies how much to adjust memory voltage tolerance.

As yet a further example, the comparison metrics can include a determination of whether the CDF-based data indicates an extrinsic tail, i.e. higher error rates in the CDF-based data that doesn't fit well to a projection of the CDF-based data. Alternatively, the quality analysis results can compare the CDF-based data to CDF-based data for other, similar memory populations. If there is an extrinsic tail or if there is beyond a threshold amount of difference from other CDF-based data, the memory population can be classified as exceptional, which may indicate a problem with the memory population.

Any of the comparison metrics (e.g. marking the memory population as pass/fail, assigning a classification to the memory population, using a function to transform the analysis results into a corresponding output, comparing among memory populations, or identifying a memory population as exceptional) can be mapped to an action trigger. Process 400 can use this mapping of comparison metric results to action triggers to cause a corresponding action to occur. For example, in implementations where the memory population has a comparison metric result marking the memory population as failed, as exceptional, or with a score failing in a disfavored range, the action trigger can cause the memory population to be disabled, removed from a memory system, have operating parameters reduced to increase reliability, or marked for further analysis. In some implementations, actions can be triggered when comparison metrics indicate that the memory population passes a threshold or that the memory population has a score falling in other particular ranges. For example, the triggered actions can be one or more of: permitting the memory population to continue in operation, marking the memory population for particular corresponding types of storage jobs, marking the memory population for further analysis, having the memory population's operating parameters changed an amount based on the assigned category, or scheduling the memory population for a follow-up analysis to check for future deterioration. In implementations where there is a comparison between memory populations, the comparison results can be used to identify problematic component sources, manufacturing facilities, production processes, memory part designs, or other factors about the construction or composition of the memory population.

In some implementations, instead of, or in addition to, automatically performing actions, the comparisons from block 408 can be incorporated in a user interface on a display.

FIG. 5 is a flow diagram of a process 500 used in some implementations for formulating an intersection comparison between CDF-based data and metrics. The method 500 can be performed by processing logic that can include hardware (e.g., processing device, circuitry, dedicated logic, programmable logic, microcode, hardware of a device, integrated circuit, etc.), software (e.g., instructions run or executed on a processing device), or a combination thereof. In some embodiments, the method 500 is performed by the memory quality engine 164 of FIG. 1. Although shown in a particular sequence or order, unless otherwise specified, the order of the processes can be modified. Thus, the illustrated implementations should be understood only as examples, and the illustrated processes can be performed in a different order, and some processes can be performed in parallel. Additionally, one or more processes can be omitted in various embodiments. Thus, not all processes are required in every implementation. Other process flows are possible. At block 504, process 500 can get a threshold condition for a memory population. In some implementations, the threshold condition is a system trigger condition threshold, specifying an error rate above which a memory device has to invoke secondary methods to perform data recovery by the drive controller. For example, a system trigger condition threshold for some solid state drives is 60 bits in error per codeword. In some implementations, the threshold condition is a drive UECC threshold, specifying an error rate above which memory pages are not recoverable by the drive controller. For example, a UECC threshold for some solid state drives is 93 bits in error per codeword.

At block 506, process 500 can compute a projection of the CDF-based data from block 406, e.g. by fitting the CDF-based data to a linear function, a quadratic function, or a function of another degree. In some implementations, other modeling techniques can be used to determine the projection, such as using the average of CDF-based data from other memory populations, or applying a machine learning algorithm to the CDF-based data or data of other memory populations to predict next data points from previous data points of the CDF-based data. In some implementations, the projection can be based on a portion of the CDF-based data. For example, a projection can be a fit to a function for a portion of the CDF-based data that best fits a line (or other degree function), excluding an initial part of the CDF-based data that does not provide a good fit. Process 500 can accomplish this by identifying a section of the CDF-based data where the CDF-based data approximates a line within a threshold amount (i.e. the CDF-based data does not deviate from a line above a threshold amount) and then fitting the function to the identified section of the CDF-based data.

In some implementations, the CDF-based data intersects with the threshold condition, and thus projecting further values for the CDF-based data is not needed. In such a case, computing a projection of the CDF-based data can be skipped, as indicated by block 506 being in a dashed line. In some implementations, a projection of the CDF-based data is used instead of the actual CDF-based data, e.g. because the CDF-based data does not intersect with the threshold condition or the CDF-based data fluctuates and an intersection of smoothed data is desired. In these cases, computing an intersection may only be desirable when the CDF-based data and the projection of the CDF-based data does not diverge beyond a threshold amount, i.e. where the CDF-based data does not have an “extrinsic tail.”

Process 500 can include a step to determine whether the CDF-based data includes an extrinsic tail, in which case process 500 can end without producing an intersection identification or can include a warning that the intersection point may be based on data with an extrinsic tail. Process 500 can identify an extrinsic tail by determining if the projection of the CDF-based data insufficiently matches the actual CDF-based data. If so, process 500 can identify the difference as an “extrinsic tail.” An extrinsic tail identification can indicate that the memory population for which the CDF-based data is derived has an issue, such as a defect, an improper operational parameter, etc. Process 500 can determine whether there is a sufficient match between the projection and the actual CDF-based data by determining if the difference between the two at any point is above a threshold. In some implementations, this determination can be based on a comparison of an average difference of all points within a window. For example, process 500 can determine the difference between the projection and the actual CDF-based data for each point on the x-axis that are within three error units of each other, and determine if the average of these differences is above a threshold. In some implementations, process 500 may only use points above a particular value, e.g. by excluding points that were excluded for projecting the CDF-based data.

At block 508, process 500 can determine the intersection between the threshold obtained at block 504 and either the CDF-based data from block 406 or the projection of the CDF-based data from block 506. In some implementations, even when the CDF-based data intersects with the threshold condition, the projection from block 506 can be used, as this data may exclude limiting factors such as an error in the manufacture process of the memory population that only shows up at high error counts. This computed intersection can be a health measure of the memory population, e.g. indicating how frequently memory units are expected to have error amounts above the threshold condition. Process 500 can return this intersection value at block 510.

FIG. 6 is a conceptual diagram of an example 600 graph of quality measurements, expressed as a codeword/bit error count histogram. In example 600, the quality measurements are expressed as a histogram showing a number of bit errors on the x-axis and an amount of codewords determined to have that number of bit errors on the y-axis.

FIG. 7 is a conceptual diagram of an example 700 of CDF-based data generated from the quality measurements of FIG. 6. In example 700, the CDF-based data is 1-CDF the quality measurements, on a logarithmic scale. The quality measurements of FIG. 6 have been converted into a first CDF-based data 702A and multiple other histograms from additional portions of the memory population have been converted into additional CDF-based data 702B-F. CDF-based data 702A-F have been combined as a summation into overall CDF-based data 704.

FIG. 8 is a conceptual diagram of example 800 analysis results for the CDF-based data of FIG. 7. In example 800, two threshold conditions have been set: the system trigger condition 810 and the drive uncorrectable error condition (UECC) 812. The system trigger condition 810 specifies how many bits in error can occur in a memory unit before methods invoked by a solid state drive are unable to recover the data, causing the drive to require error correction from the drive controller. The drive UECC 812 specifies how many bits in error can occur per memory unit before the drive controller is unable to read and correct data, causing data to be unrecoverable. In example 800, the system trigger condition threshold 810 is set at 60 bits in error and the drive UECC threshold 812 is set to 93 bits in error.

CDF-based data 704 is data based on the histogram in FIG. 6, converted to CDF-based data as shown in FIG. 7. In example 800, a projection 802, of the CDF-based data 704, is generated, e.g. by determining a linear fit to the CDF-based data 704.

A trigger rate 806 is the intercept, in example 800 at 10{circumflex over ( )}-16, of projection 802 with system trigger condition 810. The trigger rate is the rate at which error recovery is entered that causes degradation of performance below an acceptable level. A trigger rate of 10{circumflex over ( )}-16 indicates that, 1 memory unit out of 10{circumflex over ( )}16 memory units in the memory population are expected to be not correctable by the ECC engine, requiring correction by the drive controller. In example 800, the memory unit is codewords, so 1 in 10{circumflex over ( )}16 codewords are expected to have at least 60 bits in error, and thus are not correctable by the ECC engine.

A UECC rate 808 is the intercept, in example 800 at 10{circumflex over ( )}-26. of projection 802 with drive UECC 812. The UECC rate is the rate at which codewords are expected to have errors that cannot be corrected by the controller. A UECC rate of 10{circumflex over ( )}-26 indicates that, 1 memory unit out of 10{circumflex over ( )}26 memory units in the memory population are expected to be uncorrectable. In example 800, 1 in 10{circumflex over ( )}26 codewords are expected to have at least 93 bits in error and thus be uncorrectable.

The calculated intercept, whether with the system trigger condition, the drive UECC, or another threshold, can then be compared to metrics, and memory system operating parameters can be adjusted accordingly. For a given intercept of a given type, a function or mapping can specify how operating parameters should be adjusted. For example, clock rate, voltage, etc. can be adjusted to increase speed or increase reliability. In some implementations, this process of computing an intercept and making operating parameter adjustments can be repeated until the computed intercept reaches an acceptable value.

FIG. 9 is a conceptual diagram of example 900 of CDF-based data indicating a memory population as an extrinsic outlier. An extrinsic outlier occurs where a threshold amount of the CDF-based data 910, e.g. from 902 to 904, fits well with a projection 906, but then a subsequent portion of the CDF-based data 910, e.g. at 908, is a threshold amount distant from the projection, and thus has an “extrinsic tail.” When the CDF-based data for a memory population indicates an extrinsic outlier, it can indicate that there is a problem with the memory population. For example, where the memory population is a drive, an extrinsic outlier can indicate that there is a flaw in the drive.

FIG. 10 illustrates an example machine of a computer system 1000 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed. In some implementations, the computer system 1000 can correspond to computing system 100 that includes or utilizes a memory quality engine 164. In alternative implementations, the machine can be connected (e.g., networked) to other machines in a LAN, an intranet, an extranet, and/or the Internet, e.g. via network 1020. The machine can operate in the capacity of a server or a client machine in client-server network environment, as a peer machine in a peer-to-peer (or distributed) network environment, or as a server or a client machine in a cloud computing infrastructure or environment.

The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 1000 includes a processing device 1002, a main memory 1004 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 1006 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage system 1018, which communicate with each other via a bus 1030.

Processing device 1002 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device can be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processing device 1002 can also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 1002 is configured to execute instructions 1026 for performing the operations and steps discussed herein. The computer system 1000 can further include a network interface device 1008 to communicate over the network 1020.

The data storage system 1018 can include a machine-readable storage medium 1024 (also known as a computer-readable medium) on which is stored one or more sets of instructions or software 1026 embodying any one or more of the methodologies or functions described herein. The instructions 1026 can also reside, completely or at least partially, within the main memory 1004 and/or within the processing device 1002 during execution thereof by the computer system 1000, the main memory 1004 and the processing device 1002 also constituting machine-readable storage media. The machine-readable storage medium 1024, data storage system 1018, and/or main memory 1004 can correspond to the memory 150.

In one implementation, the instructions 1026 include instructions to implement functionality corresponding to the memory quality engine 164. While the machine-readable storage medium 1024 is shown in an example implementation to be a single medium, the term “machine-readable storage medium” should be taken to include a single medium or multiple media that store the one or more sets of instructions. The term “machine-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “machine-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.

Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. The present disclosure can refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage systems.

The present disclosure also relates to an apparatus for performing the operations herein. This apparatus can be specially constructed for the intended purposes, or it can include a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct a more specialized apparatus to perform the method. The structure for a variety of these systems will appear as set forth in the description below. In addition, the present disclosure is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of the disclosure as described herein.

The present disclosure can be provided as a computer program product, or software, that can include a machine-readable medium having stored thereon instructions, which can be used to program a computer system (or other electronic devices) to perform a process according to the present disclosure. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). In some implementations, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium such as a read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices, etc.

In the foregoing specification, implementations of the disclosure have been described with reference to specific example implementations thereof. It will be evident that various modifications can be made thereto without departing from the broader spirit and scope of implementations of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

Reference in this specification to “implementations” (e.g. “some implementations,” “various implementations,” “one implementation,” “an implementation,” etc.) means that a particular feature, structure, or characteristic described in connection with the implementation is included in at least one implementation of the disclosure. The appearances of these phrases in various places in the specification are not necessarily all referring to the same implementation, nor are separate or alternative implementations mutually exclusive of other implementations. Moreover, various features are described which may be exhibited by some implementations and not by others. Similarly, various requirements are described which may be requirements for some implementations but not for other implementations.

As used herein, being above a threshold means that a value for an item under comparison is above a specified other value, that an item under comparison is among a certain specified number of items with the largest value, or that an item under comparison has a value within a specified top percentage value. As used herein, being below a threshold means that a value for an item under comparison is below a specified other value, that an item under comparison is among a certain specified number of items with the smallest value, or that an item under comparison has a value within a specified bottom percentage value. As used herein, being within a threshold means that a value for an item under comparison is between two specified other values, that an item under comparison is among a middle specified number of items, or that an item under comparison has a value within a middle specified percentage range. Relative terms, such as high or unimportant, when not otherwise defined, can be understood as assigning a value and determining how that value compares to an established threshold. For example, the phrase “selecting a fast connection” can be understood to mean selecting a connection that has a value assigned corresponding to its connection speed that is above a threshold.

As used herein, the word “or” refers to any possible permutation of a set of items. For example, the phrase “A, B, or C” refers to at least one of A, B, C, or any combination thereof, such as any of: A; B; C; A and B; A and C; B and C; A, B, and C; or multiple of any item such as A and A; B, B, and C; A, A, B, C, and C; etc.

Any patents, patent applications, and other references noted above are incorporated herein by reference. Aspects can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations. If statements or subject matter in a document incorporated by reference conflicts with statements or subject matter of this application, then this application shall control. 

We claim:
 1. A method comprising: obtaining quality measures for a memory population, wherein the quality measures comprise a histogram indicating counts of errors per memory unit in the memory population of a memory system; converting the quality measures into logarithmic cumulative distribution function (CDF)-based data by computing a cumulative distribution function of the histogram; formulating one or more comparisons of the CDF-based data to metrics for a quality analysis, by: obtaining a threshold condition; fitting a function to at least a portion of the CDF-based data; and computing an intersection between the function and the threshold condition; and applying results of the quality analysis to make improvements in the memory system by causing, based on the computed intersection, one or more actions in relation to the memory population, the one or more actions comprising a modification to operating parameters for the memory population.
 2. The method of claim 1, wherein the memory population comprises: a plurality of memory cells, a plurality of memory pages, a plurality of memory word lines, a plurality of memory blocks, a plurality of memory planes, a plurality of memory dies, or a plurality of memory devices, or a combination thereof.
 3. The method of claim 1, wherein the errors per memory unit in the quality measures for the memory population comprise bit errors per codeword.
 4. The method of claim 1, wherein converting the quality measures into CDF-based data comprises computing the CDF-based data as one minus the cumulative distribution function of the histogram.
 5. The method of claim 1, wherein the threshold condition is a system trigger threshold that specifies an error count correlated to data recovery speed as an error rate above which the memory system has to invoke secondary methods to perform data recovery by a controller of the memory system.
 6. The method of claim 1, wherein the threshold condition is an uncorrectable error correction condition (UECC) threshold specifying an error rate above which errors are not recoverable by a drive controller of the memory population.
 7. The method of claim 1, wherein fitting the function to at least the portion of the CDF-based data comprises: identifying a section of the CDF-based data where the CDF-based data approximates, within a threshold amount, a line; and fitting a linear function to the identified section of the CDF-based data.
 8. The method of claim 7, wherein the computing the intersection between the linear function and the threshold condition is in response to a determination that the CDF-based data does not comprise an extrinsic tail by determining that, past the section of the CDF-based data on the x-axis, the fit linear function and the CDF-based data do not differ above a threshold amount.
 9. The method of claim 1, wherein the modification to the operating parameters comprises adjusting a voltage, a clock rate, or a latency, or a combination thereof for the memory population, based on the computed intersection.
 10. A non-transitory computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations comprising: obtaining quality measures for a memory population of a memory system; converting the quality measures into cumulative distribution function (CDF)-based data; formulating one or more comparisons of the CDF-based data to metrics for a quality analysis, by: obtaining an error amount threshold condition; fitting a function to at least a portion of the CDF-based data; and computing an intersection between the function and the error amount threshold condition; and applying results of the quality analysis to make improvements in the memory system by causing, based on the computed intersection, one or more actions in relation to the memory population.
 11. The non-transitory computer-readable storage medium of claim 10, wherein the quality measures comprise a histogram indicating counts of errors per memory unit in the memory population; and wherein converting the quality measures into CDF-based data is performed by computing a cumulative distribution function of the histogram.
 12. The non-transitory computer-readable storage medium of claim 10, wherein the error amount threshold condition either specifies an error amount correlated to data recovery speed or specifies an error amount above which errors are not recoverable by a controller of the memory population.
 13. The non-transitory computer-readable storage medium of claim 10, wherein the function is a linear function on a logarithmic scale.
 14. The non-transitory computer-readable storage medium of claim 10, wherein the computing the intersection between the function and the threshold condition is in response to a determination that the CDF-based data does not comprise an extrinsic tail.
 15. The non-transitory computer-readable storage medium of claim 10, wherein causing the one or more actions comprises causing a modification to operating parameters for the memory population.
 16. The non-transitory computer-readable storage medium of claim 10, wherein causing the one or more actions comprises generating a report indicating the computed intersection.
 17. The non-transitory computer-readable storage medium of claim 10, wherein the function is a linear function on a logarithmic scale and wherein fitting the function to at least the portion of the CDF-based data comprises: identifying a section of the CDF-based data where the CDF-based data approximates, within a threshold amount, a line; and fitting the linear function to the identified section of the CDF-based data.
 18. A system comprising: a memory; one or more processors; an interface configured to, using the one or more processors: obtain quality measures for a memory population of a memory system; and obtain an error amount threshold condition; a cumulative distribution function (CDF) converter configured to, using the one or more processors, convert the quality measures into CDF-based data; an intercept analysis engine configured to, using the one or more processors, formulate one or more comparisons of the CDF-based data to metrics for a quality analysis, by: fitting a function to at least a portion of the CDF-based data; and computing an intersection between the function and the threshold condition; and an analysis application engine configured to, using the one or more processors, apply results of the quality analysis to make improvements in the memory system by causing, based on the computed intersection, one or more actions in relation to the memory population.
 19. The system of claim 18, wherein the quality measures comprise a histogram indicating counts of errors per memory unit in the memory population; and wherein converting the quality measures into CDF-based data is performed by computing a cumulative distribution function of the histogram.
 20. The system of claim 18, wherein the error amount threshold condition either specifies an error amount correlated to data recovery speed or specifies an error amount above which errors are not recoverable by a controller of the memory population. 